Dynomotion

Group: DynoMotion Message: 1397 From: bradodarb Date: 7/1/2011
Subject: Kmotion files
Hello,


While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.

I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.

I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.

Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:

I receive this error as a call back if my solution is not in the installed source directory.



\dsp_kmotion\dspkmotion.out not found.....


If I place the requested folder+file in the root directory, all is well.
Does this have to do with the TCC compiler?

The worst error I get on some test machines is this:
___________________________________________
Unable to execute:

KMotionServer.exe


Try re-installing software or copy this file to the same location as KMotion.exe
____________________________________________

I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.


Do you have a road map to the references when creating a new project?

Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.


Thanks for your time.

-Brad Murry
Group: DynoMotion Message: 1398 From: Tom Kerekes Date: 7/1/2011
Subject: Re: Kmotion files
Hi Brad,
 
Unfortunately it is a bit complex.  There are a number of components that make up KMotion System.  The components needed to run are:
 
<Install>\KMotion\Release - contains DLLs EXEs (release versions)
 
<Install>\KMotion\Debug - contains DLLs EXEs (debug versions)
 
<Install>\KMotion\Data - various data files, screen persist states, settings, logs, etc
 
<Install>\KMotion\Help - HTML Help files
 
<Install>\DSP_KFLOP - DSP headers and link object for TCC67 Compiler
 
<install>\USB Driver - Used to initially install USB Drivers for Windows
 
Some of the executables and DLLs expect this directory structure based on where they are executed from.
 
 
The remainder of the directory structure are examples of C programs, GCode Programs, PC Programs, and Source Code that are not necessarily needed at run time.
 
Probably the simplest approach to distribute your application would be to leave our directory structure intact and place your application executable into our <Install>\KMotion\Release directory the same in the same manner as our example applications do.
 
Alternatively if you wish to place your application elsewhere you could set the Window's PATH variable to include the <Install>\KMotion\Release directory.
 
Or if you prefer not to modify the global Windows PATH, Windows has an APP_PATHS key in the Registry were you can assign a search path that is specific to your application.
 
I hope this helps,
 
TK


--- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:

From: bradodarb <bradodarb@...>
Subject: [DynoMotion] Kmotion files
To: DynoMotion@yahoogroups.com
Date: Friday, July 1, 2011, 8:21 AM

 
Hello,

While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.

I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.

I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.

Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:

I receive this error as a call back if my solution is not in the installed source directory.

\dsp_kmotion\dspkmotion.out not found.....

If I place the requested folder+file in the root directory, all is well.
Does this have to do with the TCC compiler?

The worst error I get on some test machines is this:
___________________________________________
Unable to execute:

KMotionServer.exe

Try re-installing software or copy this file to the same location as KMotion.exe
____________________________________________

I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.

Do you have a road map to the references when creating a new project?

Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.

Thanks for your time.

-Brad Murry
Group: DynoMotion Message: 1399 From: bradodarb Date: 7/1/2011
Subject: Re: Kmotion files
Thanks Tom,

Adding the registry key seems like the way we will go.


I am having a bit of trouble still trying to compile and run programs using the following call:

CKMotionDLL *KM_dll=(CKMotionDLL *)handle;
long rslt=KM_dll->LoadCoff(board,Thread,Name,false);


I am just using the print.c to get a nice Hello World back from the board.


I am able to compile(it generates an .out file) but it will not execute.

I receive the following response::

In file included from <c file name>:1:
E:\DynoMotion\C Programs/KMotionDef.h:56:



I get this error even when trying to run the c file from the install dir's C Programs folder.



Please advise


-Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Brad,
>  
> Unfortunately it is a bit complex.  There are a number of components that make up KMotion System.  The components needed to run are:
>  
> <Install>\KMotion\Release - contains DLLs EXEs (release versions)
>  
> <Install>\KMotion\Debug - contains DLLs EXEs (debug versions)
>  
> <Install>\KMotion\Data - various data files, screen persist states, settings, logs, etc
>  
> <Install>\KMotion\Help - HTML Help files
>  
> <Install>\DSP_KFLOP - DSP headers and link object for TCC67 Compiler
>  
> <install>\USB Driver - Used to initially install USB Drivers for Windows
>  
> Some of the executables and DLLs expect this directory structure based on where they are executed from.
>  
>  
> The remainder of the directory structure are examples of C programs, GCode Programs, PC Programs, and Source Code that are not necessarily needed at run time.
>  
> Probably the simplest approach to distribute your application would be to leave our directory structure intact and place your application executable into our <Install>\KMotion\Release directory the same in the same manner as our example applications do.
>  
> Alternatively if you wish to place your application elsewhere you could set the Window's PATH variable to include the <Install>\KMotion\Release directory.
>  
> Or if you prefer not to modify the global Windows PATH, Windows has an APP_PATHS key in the Registry were you can assign a search path that is specific to your application.
>  
> I hope this helps,
>  
> TK
>
>
> --- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:
>
>
> From: bradodarb <bradodarb@...>
> Subject: [DynoMotion] Kmotion files
> To: DynoMotion@yahoogroups.com
> Date: Friday, July 1, 2011, 8:21 AM
>
>
>  
>
>
>
> Hello,
>
> While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.
>
> I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.
>
> I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.
>
> Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:
>
> I receive this error as a call back if my solution is not in the installed source directory.
>
> \dsp_kmotion\dspkmotion.out not found.....
>
> If I place the requested folder+file in the root directory, all is well.
> Does this have to do with the TCC compiler?
>
> The worst error I get on some test machines is this:
> ___________________________________________
> Unable to execute:
>
> KMotionServer.exe
>
> Try re-installing software or copy this file to the same location as KMotion.exe
> ____________________________________________
>
> I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.
>
> Do you have a road map to the references when creating a new project?
>
> Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.
>
> Thanks for your time.
>
> -Brad Murry
>
Group: DynoMotion Message: 1400 From: Tom Kerekes Date: 7/1/2011
Subject: Re: Kmotion files
It is flagging an error at Line 56 in KMotionDef.h which is:
 
#include
 "PC-DSP.h" // contains common structures shared by PC and DSP
 
so the compiler probably can't find that file.  It should be in the DSP_KFLOP folder next to the KMotionDef.h file.  Those are the only 2 headers normally needed.
 
Regards
TK 
 
 


--- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:

From: bradodarb <bradodarb@...>
Subject: [DynoMotion] Re: Kmotion files
To: DynoMotion@yahoogroups.com
Date: Friday, July 1, 2011, 3:14 PM

 
Thanks Tom,

Adding the registry key seems like the way we will go.

I am having a bit of trouble still trying to compile and run programs using the following call:

CKMotionDLL *KM_dll=(CKMotionDLL *)handle;
long rslt=KM_dll->LoadCoff(board,Thread,Name,false);

I am just using the print.c to get a nice Hello World back from the board.

I am able to compile(it generates an .out file) but it will not execute.

I receive the following response::

In file included from <c file name>:1:
E:\DynoMotion\C Programs/KMotionDef.h:56:

I get this error even when trying to run the c file from the install dir's C Programs folder.

Please advise

-Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Brad,
>  
> Unfortunately it is a bit complex.  There are a number of components that make up KMotion System.  The components needed to run are:
>  
> <Install>\KMotion\Release - contains DLLs EXEs (release versions)
>  
> <Install>\KMotion\Debug - contains DLLs EXEs (debug versions)
>  
> <Install>\KMotion\Data - various data files, screen persist states, settings, logs, etc
>  
> <Install>\KMotion\Help - HTML Help files
>  
> <Install>\DSP_KFLOP - DSP headers and link object for TCC67 Compiler
>  
> <install>\USB Driver - Used to initially install USB Drivers for Windows
>  
> Some of the executables and DLLs expect this directory structure based on where they are executed from.
>  
>  
> The remainder of the directory structure are examples of C programs, GCode Programs, PC Programs, and Source Code that are not necessarily needed at run time.
>  
> Probably the simplest approach to distribute your application would be to leave our directory structure intact and place your application executable into our <Install>\KMotion\Release directory the same in the same manner as our example applications do.
>  
> Alternatively if you wish to place your application elsewhere you could set the Window's PATH variable to include the <Install>\KMotion\Release directory.
>  
> Or if you prefer not to modify the global Windows PATH, Windows has an APP_PATHS key in the Registry were you can assign a search path that is specific to your application.
>  
> I hope this helps,
>  
> TK
>
>
> --- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:
>
>
> From: bradodarb <bradodarb@...>
> Subject: [DynoMotion] Kmotion files
> To: DynoMotion@yahoogroups.com
> Date: Friday, July 1, 2011, 8:21 AM
>
>
>  
>
>
>
> Hello,
>
> While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.
>
> I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.
>
> I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.
>
> Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:
>
> I receive this error as a call back if my solution is not in the installed source directory.
>
> \dsp_kmotion\dspkmotion.out not found.....
>
> If I place the requested folder+file in the root directory, all is well.
> Does this have to do with the TCC compiler?
>
> The worst error I get on some test machines is this:
> ___________________________________________
> Unable to execute:
>
> KMotionServer.exe
>
> Try re-installing software or copy this file to the same location as KMotion.exe
> ____________________________________________
>
> I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.
>
> Do you have a road map to the references when creating a new project?
>
> Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.
>
> Thanks for your time.
>
> -Brad Murry
>
Group: DynoMotion Message: 1401 From: bradodarb Date: 7/1/2011
Subject: Re: Kmotion files
The file is in the directory you indicated. I also placed a copy directly in the C Programs folder to no avail...

-Brad Murry


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> It is flagging an error at Line 56 in KMotionDef.h which is:
>  
> #include "PC-DSP.h" // contains common structures shared by PC and DSP
>  
> so the compiler probably can't find that file.  It should be in the DSP_KFLOP folder next to the KMotionDef.h file.  Those are the only 2 headers normally needed.
>  
> Regards
> TK 
>  
>  
>
>
> --- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:
>
>
> From: bradodarb <bradodarb@...>
> Subject: [DynoMotion] Re: Kmotion files
> To: DynoMotion@yahoogroups.com
> Date: Friday, July 1, 2011, 3:14 PM
>
>
>  
>
>
>
> Thanks Tom,
>
> Adding the registry key seems like the way we will go.
>
> I am having a bit of trouble still trying to compile and run programs using the following call:
>
> CKMotionDLL *KM_dll=(CKMotionDLL *)handle;
> long rslt=KM_dll->LoadCoff(board,Thread,Name,false);
>
> I am just using the print.c to get a nice Hello World back from the board.
>
> I am able to compile(it generates an .out file) but it will not execute.
>
> I receive the following response::
>
> In file included from <c file name>:1:
> E:\DynoMotion\C Programs/KMotionDef.h:56:
>
> I get this error even when trying to run the c file from the install dir's C Programs folder.
>
> Please advise
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Brad,
> >  
> > Unfortunately it is a bit complex.  There are a number of components that make up KMotion System.  The components needed to run are:
> >  
> > <Install>\KMotion\Release - contains DLLs EXEs (release versions)
> >  
> > <Install>\KMotion\Debug - contains DLLs EXEs (debug versions)
> >  
> > <Install>\KMotion\Data - various data files, screen persist states, settings, logs, etc
> >  
> > <Install>\KMotion\Help - HTML Help files
> >  
> > <Install>\DSP_KFLOP - DSP headers and link object for TCC67 Compiler
> >  
> > <install>\USB Driver - Used to initially install USB Drivers for Windows
> >  
> > Some of the executables and DLLs expect this directory structure based on where they are executed from.
> >  
> >  
> > The remainder of the directory structure are examples of C programs, GCode Programs, PC Programs, and Source Code that are not necessarily needed at run time.
> >  
> > Probably the simplest approach to distribute your application would be to leave our directory structure intact and place your application executable into our <Install>\KMotion\Release directory the same in the same manner as our example applications do.
> >  
> > Alternatively if you wish to place your application elsewhere you could set the Window's PATH variable to include the <Install>\KMotion\Release directory.
> >  
> > Or if you prefer not to modify the global Windows PATH, Windows has an APP_PATHS key in the Registry were you can assign a search path that is specific to your application.
> >  
> > I hope this helps,
> >  
> > TK
> >
> >
> > --- On Fri, 7/1/11, bradodarb <bradodarb@> wrote:
> >
> >
> > From: bradodarb <bradodarb@>
> > Subject: [DynoMotion] Kmotion files
> > To: DynoMotion@yahoogroups.com
> > Date: Friday, July 1, 2011, 8:21 AM
> >
> >
> >  
> >
> >
> >
> > Hello,
> >
> > While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.
> >
> > I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.
> >
> > I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.
> >
> > Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:
> >
> > I receive this error as a call back if my solution is not in the installed source directory.
> >
> > \dsp_kmotion\dspkmotion.out not found.....
> >
> > If I place the requested folder+file in the root directory, all is well.
> > Does this have to do with the TCC compiler?
> >
> > The worst error I get on some test machines is this:
> > ___________________________________________
> > Unable to execute:
> >
> > KMotionServer.exe
> >
> > Try re-installing software or copy this file to the same location as KMotion.exe
> > ____________________________________________
> >
> > I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.
> >
> > Do you have a road map to the references when creating a new project?
> >
> > Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.
> >
> > Thanks for your time.
> >
> > -Brad Murry
> >
>
Group: DynoMotion Message: 1405 From: Tom Kerekes Date: 7/2/2011
Subject: Re: Kmotion files
Hi Brad,
 
Sorry I'm not able to duplicate that problem.  If I delete the PC-DSP.h then I get that exact error.  But if I place it in the DSP_KFLOP directory or the Directory with the C program it finds it ok.
 
I thought it might be a bug related to not using the C drive but I installed to my H: drive and I don't see any problem.  
 
Does it compile if you use KMotion.exe and compile it from the C Programs Screen?
 
You might try the SimpleCoffLoad.exe example to see if it works correctly.
 
You might debug it by stepping into the KMotionDLL.DLL and in just a few lines of code it builds up the command line with the Include Directories to invoke the compiler.
 
Or send me your code and I can debug it for you.
 
Regards,
TK
 


--- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:

From: bradodarb <bradodarb@...>
Subject: [DynoMotion] Re: Kmotion files
To: DynoMotion@yahoogroups.com
Date: Friday, July 1, 2011, 4:43 PM

 

The file is in the directory you indicated. I also placed a copy directly in the C Programs folder to no avail...

-Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> It is flagging an error at Line 56 in KMotionDef.h which is:
>  
> #include "PC-DSP.h" // contains common structures shared by PC and DSP
>  
> so the compiler probably can't find that file.  It should be in the DSP_KFLOP folder next to the KMotionDef.h file.  Those are the only 2 headers normally needed.
>  
> Regards
> TK 
>  
>  
>
>
> --- On Fri, 7/1/11, bradodarb <bradodarb@...> wrote:
>
>
> From: bradodarb <bradodarb@...>
> Subject: [DynoMotion] Re: Kmotion files
> To: DynoMotion@yahoogroups.com
> Date: Friday, July 1, 2011, 3:14 PM
>
>
>  
>
>
>
> Thanks Tom,
>
> Adding the registry key seems like the way we will go.
>
> I am having a bit of trouble still trying to compile and run programs using the following call:
>
> CKMotionDLL *KM_dll=(CKMotionDLL *)handle;
> long rslt=KM_dll->LoadCoff(board,Thread,Name,false);
>
> I am just using the print.c to get a nice Hello World back from the board.
>
> I am able to compile(it generates an .out file) but it will not execute.
>
> I receive the following response::
>
> In file included from <c file name>:1:
> E:\DynoMotion\C Programs/KMotionDef.h:56:
>
> I get this error even when trying to run the c file from the install dir's C Programs folder.
>
> Please advise
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Brad,
> >  
> > Unfortunately it is a bit complex.  There are a number of components that make up KMotion System.  The components needed to run are:
> >  
> > <Install>\KMotion\Release - contains DLLs EXEs (release versions)
> >  
> > <Install>\KMotion\Debug - contains DLLs EXEs (debug versions)
> >  
> > <Install>\KMotion\Data - various data files, screen persist states, settings, logs, etc
> >  
> > <Install>\KMotion\Help - HTML Help files
> >  
> > <Install>\DSP_KFLOP - DSP headers and link object for TCC67 Compiler
> >  
> > <install>\USB Driver - Used to initially install USB Drivers for Windows
> >  
> > Some of the executables and DLLs expect this directory structure based on where they are executed from.
> >  
> >  
> > The remainder of the directory structure are examples of C programs, GCode Programs, PC Programs, and Source Code that are not necessarily needed at run time.
> >  
> > Probably the simplest approach to distribute your application would be to leave our directory structure intact and place your application executable into our <Install>\KMotion\Release directory the same in the same manner as our example applications do.
> >  
> > Alternatively if you wish to place your application elsewhere you could set the Window's PATH variable to include the <Install>\KMotion\Release directory.
> >  
> > Or if you prefer not to modify the global Windows PATH, Windows has an APP_PATHS key in the Registry were you can assign a search path that is specific to your application.
> >  
> > I hope this helps,
> >  
> > TK
> >
> >
> > --- On Fri, 7/1/11, bradodarb <bradodarb@> wrote:
> >
> >
> > From: bradodarb <bradodarb@>
> > Subject: [DynoMotion] Kmotion files
> > To: DynoMotion@yahoogroups.com
> > Date: Friday, July 1, 2011, 8:21 AM
> >
> >
> >  
> >
> >
> >
> > Hello,
> >
> > While creating a c# framework for the Kflop, I have become a bit confused as to what the best practices are for managing the location for all the referenced files.
> >
> > I am looking to keep it tidy, and also to make it easy to update the refs as Dynomotion releases new updates.
> >
> > I started to re-route some of the refs in your DLL's but thought better of it when the scenario of doing this every time Dynomotion releases an update entered my mind.
> >
> > Some are straight forward to discover through the debugger, but others do not surface until run-time like the below error when I try to compile and download a C file to the controller:
> >
> > I receive this error as a call back if my solution is not in the installed source directory.
> >
> > \dsp_kmotion\dspkmotion.out not found.....
> >
> > If I place the requested folder+file in the root directory, all is well.
> > Does this have to do with the TCC compiler?
> >
> > The worst error I get on some test machines is this:
> > ___________________________________________
> > Unable to execute:
> >
> > KMotionServer.exe
> >
> > Try re-installing software or copy this file to the same location as KMotion.exe
> > ____________________________________________
> >
> > I have both of these files as well as many other Dynomotion files in the same folder as the KMotionDLL.dll is located that my c# library is using.
> >
> > Do you have a road map to the references when creating a new project?
> >
> > Is there a way you guys could add to your source a mechanism to specify the location of important files/ folders(if it is not already there)? Again, I could do this but it would be nice if it was there in each new update.
> >
> > Thanks for your time.
> >
> > -Brad Murry
> >
>